An outbound ACKNOWLEDGEMENT EDI message is an application error and acknowledgment message that N4 can send to an EDI trading partner to:
Acknowledge that N4 received an EDI message.
Inform the EDI trading partner that N4 accepted or rejected the EDI message during processing.
To determine which inbound EDI messages for an EDI trading partner that you want N4 to send an outbound ACKNOWLEDGEMENT message, you must add session criteria to the EDI session. You can filter by the class and status of the inbound EDI messages for an EDI trading partner. For example, you can add session criteria to send outbound ACKNOWLEDGEMENT messages only when an inbound BOOKING EDI message processes with ERRORS. For more information, see EDI Session form (on page 1) and Session Criteria examples (on page 1).
After processing an inbound EDI message that satisfies the session criteria for an outbound ACKNOWLEDGEMENT EDI session, N4 processes the outbound ACKNOWLEDGEMENT EDI message. N4 displays the Interchange Number with the Message Sequence Number from the EDI Session for the outbound Acknowledgment message and increments based on the transactions that is in the acknowledged ISA file. N4 includes the following message function codes in the BGM segment of the ACKNOWLEDGEMENT EDI message per the Navis standard mapping file:
AP: N4 accepted the inbound EDI message
RE: N4 rejected the inbound EDI message
The Navis supported ACKNOWLEDGEMENT EDI message is the APERAK EDI message.
Also, per the Navis standard mapping file, N4 includes the following primary key and optional information in the RFF segment based on the class of the inbound EDI message:
|
EDI Message Class |
Primary Key |
Optional Information |
|---|---|---|
|
STOWPLAN |
Container number |
Vessel name and container's line operator |
|
PREADVISE |
Container number |
Vessel name and container's line operator |
|
LOADLIST |
Container number |
Booking number, vessel name, and container's line operator |
|
DISCHLIST |
Container number |
Vessel name and container's line operator |
|
RELEASE |
Release number |
Vessel name and line operator |
|
BOOKING |
Export booking number |
Vessel name and line operator |
|
MANIFEST |
Bill of lading number |
Vessel name |
N4 sends this information so that the EDI partner can determine the associated EDI message.
If N4 rejected the inbound EDI message, N4 also includes an error code in the ERC segment and an error message in the FTX segment in the ACKNOWLEDGEMENT EDI message.
Depending on the message function and error codes your EDI trading partner requires, you may need to edit the mapping file so that N4 will send the correct codes.
In addition, N4 displays the processed EDI data in the Transactions view and on Transactions tab for the associated inbound EDI transactions. For example, if you send APERAK EDI messages in response to inbound BOOKING EDI messages, N4 displays the processed APERAK data in the Transactions view and on Transactions tab for the associated inbound BOOKING EDI transactions. For more information, see Transactions view (on page 1).
For more information on the APERAK EDI message, go to http://www.unece.org/trade/untdid/d00a/trmd/aperak_c.htm.